[00:00] In this lesson, we'll learn how to configure our central gateway as a controller in an enterprise administration setup. One important aspect of the controller gateway is that it should have a database connection where we want to store our agent tasks, configuration, or event history. I've already set up a database, so I'll get started with the controller setup. We'll navigate to the Network tab and click on the configure page under enterprise. Without a controller setup, this page notifies us that our EAM is not configured, and we are prompted to click on this button to get started. This first page lets us choose an agent or a controller gateway, and we'll choose the latter and click on next. We have some configuration options, and the first is to choose the database for agent history. I mentioned already I have a database connection on this gateway, and when I click into this field, it's automatically recognized, and I can select it. Now we have a section for archiving settings. The archive folder saves important files such as agent gateway backups and archive modules.

[01:05] We can choose to have this location automatically set, or we can manually enter in the file path. This can be set up on the machine or on a locally mounted network share, but keep in mind that the path will be relative to the controller gateway. I'll go ahead and leave this set to Automatic. It's recommended that you put a system in place to monitor the availability of disk storage, as gateway backups can potentially grow to be quite large, especially if many agents are connected. Conveniently, we do have some additional settings to help manage this situation. This value listed in megabytes can be altered to set our load disk threshold so that when there is only this amount of space left, an error message is reported to the controller, providing better visibility. We can also remove or delete backup files from the archive based on a maximum count or age. By default, my configuration is set up so that after a sixth backup file is created, the oldest one will be removed from the archive, maintaining the maximum retention count. With a max retention age of zero, we are basically saying that we don't care how old the backup files are, always keep them in the archive.

[02:06] The maximum retention count does take precedence here, meaning this value will be maintained regardless of how old backup files are. You can configure either of these settings with values that make sense for you, and I'll include a link below this video to the controller settings user manual page for guidance. After you complete the archiving section, you can then click on finish, and the gateway will now be set as a controller. You can see all these other pages became available under the Enterprise section, as creating the controller was a necessary step in setting up EAM. In the next lesson, we'll learn how to set up our agent gateways and connect them to the controller. And if you ever want to reassign which gateway is the controller, then you would first need to uninstall it using this button.